An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello, We have submitted our app on August 10th, and still "Waiting for Review" for over 20 days. Can anyone help us resolve this issue?

Hello, Our app has been in "Waiting for Review" since August 18, 2026 at 6:51 PM, and has never entered "In Review." It has now been 10 days. Apple ID: 6768989011 Version: 1.0 Platform: iOS Submitted: August 18, 2026 Current Status: Waiting for Review I have already confirmed the following on our side: No messages or requests for additional information in Resolution Center Agreements, Tax, and Banking are all Active Age Rating questionnaire and Export Compliance are complete App Review Information includes demo credentials and detailed review notes No in-app purchases pending review I understand review times can vary, and I can see from recent posts in this forum that other developers are experiencing similar delays with first submissions. Could someone from the App Review team please check whether this submission is progressing normally, or escalate it if necessary? Thank you for your time.

Hello, I am looking for guidance on a new app submission that has not moved out of the queue. App: Balanced: Pilates Instructor Apple ID: 6797579437 Platform: iOS Version: 1.0 (first submission of a new app) Submitted: 20 August 2026 Current status: Waiting for Review It has now been 12 days without the status changing to In Review. There are no messages in the Resolution Center and I have received no communication from the App Review team. I submitted a request through the Contact Us form on 26 August and have not had a response. I would also note that the Distribution tab for this app intermittently fails to load, showing "Sorry, something went wrong. Try your request again." I am unsure whether this is related or a separate App Store Connect issue, but it means I cannot always view the submission record. I have not cancelled or resubmitted the build, as I understand that would return me to the back of the queue. Is there anything further I can do to have this submission picked up for review? Thank you.

I'm starting to wonder if something has gone horribly wrong in the App Review department. We've had reviewers request specific information in one message, which we supplied the same day, then we wait another 4 days and they ask the same question having clearly not looked at the information we sent. We've now been completely adrift for 21 days and it's been over a week since we last heard from them. We have hundreds of people waiting on us, can't promote on social media, receiving support requests every day from customers wondering why they can't access the app. This isn't the first time we've released an app through App Store Connect, and our app is very straighforward - no restrictions or unusual requests. The app is obviously compliant, they just aren't reading any of the information we're providing, so we're totally stuck. It didn't used to be like this. A year ago we were seeing reviews turn around within the stated 24-48 hours. Has something changed in the last 6 months? Perhaps an uptick in submissions due to AI coding? Anyone else seeing these issues?

Hello, I'm a solo developer and I'm running into the same review delay on every single submission, not just one. I'd appreciate any insight into whether something on my account is causing this. Current submission: App: Silk Road Tycoon: Idle Empire Apple ID: 6795834497 Version: 1.0.7 (Build [1]) Submitted: [23 Aug 2026] Current status: [Waiting for Review] Days in queue: 8 This is an update to an app that is already live on the App Store (1.0.3 shipped 22 Aug). It contains no new permissions, no new frameworks and no change to the monetization model. The pattern is not isolated: My other app, Big Bluff - Liar Party Game (Apple ID 6798633287), went through the same multi-day waits on every submission before it went live earlier this month. Every release I have submitted so far has sat in the queue far longer than the 24-48 hour guidance, including minor updates. What I have already verified: All Agreements, Tax and Banking information is active and current Export compliance, content rights and age rating questions are all answered App Review Notes are filled in; the game requires no login, so no demo account is needed No messages in the Resolution Center and no communication from App Review I have not cancelled or resubmitted, since I understand that resets queue position I have also filed an expedited review request with no response. My question: is this simply the current queue length, or is there something flagged on my developer account that routes my submissions into a slower lane? If it's the latter, I'd like to fix whatever is causing it rather than keep filing tickets on every release. Thank you.

Hello, I am seeking guidance regarding a Pending Termination Notice received on March 18, 2026 for the developer account of Kaagapay Platform Inc. Background: Our app, CreditKaagapay: Score & Report (App ID: 6744999391), is a credit report and loan matching platform operating in the Philippines in partnership with the Credit Information Corporation (CIC). The app maintained a 4.8-star rating with over 4,000 reviews. No prior warnings were issued before the notice. Notice Details: The notice cited Guideline 5.6 and Section 3.2(f), alleging dishonest or fraudulent activity related to account information. Timeline: • March 18: Received the Pending Termination Notice. Submitted two appeals (App Removal + Pending Account Termination) on the same day. Both received on-screen confirmation. • March 25: Submitted a follow-up through the App Review Status contact form. • March 26: Developer Support confirmed the appeal was forwarded to the App Review Board (Case ID: 30000003321343). • April 1 (today, Day 14): No response received from the App Review Board. Questions: Is there a way to confirm that our appeals are currently under review by the App Review Board? Are there any additional steps we should take to bring this to the Board's attention? Is there any mechanism to submit supplementary documentation, as the appeal form did not support attachments? We remain fully committed to compliance and ready to provide any additional information requested. Thank you for any guidance. Yifu Zhang, Account Holder Case ID: 30000003321343

I have a problem with the title of my app "Trophy Tracker for PlayStation". I submitted version 2.0.0 a few days ago and it got rejected because of the following: Guideline 4.1(c) - Design - Copycats "App's cannot use another developer's icon, brand, or product name in the app's icon or name, without approval from that developer." I'm wondering for two reasons about this. First, why did the previous versions not get rejected? The app is a month old now and from what I know there has not been an update of the guideline. Second, isn't it a base practice in the App Store to use the title formate "xxx for xxx"? A few examples would be "Creator View for YouTube" or "Apollo for Reddit". And even my competitors use terms like "Steam", "XBOX" or "PSN" in their subtitle. I sent a message to the review team, but I just got a generic response containing the text of the guideline. I have to mention that I do not claim to be Sony or PlayStation in any way, the reason why it is in the app title is to let users know that the app is only for PlayStation, no Steam or Xbox for example. What do you recommend in this situation? Is it worth to make an appeal? Do I have to live with it and change my app name? Did I just have bad luck with the reviewer? If you've made similar experiences or know what to do next I'd love to hear your ideas. Thanks in advance!

I'm looking for clarification on how the new EU business terms apply to a code-redemption flow. My app sells self-guided digital audio tours via Apple In-App Purchase. I would also like to sell the same tours independently through third-party travel marketplaces (general tour and activity booking platforms). The proposed flow: The app would not advertise, mention, or link to these marketplaces in any way. After purchasing a tour externally, an EU customer receives a booking code. In the app, the customer taps "Enter a booking code," types the code, and taps "Fetch Tour." The app verifies the booking against our server and unlocks the purchased tour, with no additional payment taken. The same tours remain available for direct purchase through Apple In-App Purchase. App Review has previously rejected this type of code-redemption functionality under the In-App Purchase rules. Two questions: Is this exact flow now permitted on EU storefronts under Attachment 14, using the StoreKit External Purchase or External Purchase Link entitlement? Do these externally initiated sales need to be reported to Apple, or incur an Apple commission, given that the app contains no external offer, marketplace name, purchase instructions, or actionable link? Thanks in advance for any guidance.

Hi everyone, I am seeking advice from developers who have successfully resolved or navigated Guideline 4.3(b) (Design: Spam / Saturated Category) rejections, especially within the dating or social networking space. App Overview & Core Features: Our app is a "Diary-based Dating / Emotional Connection Platform." Unlike traditional photo-first, swipe-deck dating apps, our core mechanics rely on authentic emotional reflection: Journal/Diary-First Discovery: Users write daily diary entries reflecting their thoughts and emotions. Matching and interaction occur based on mutual empathy with these journal entries. Identity Verification: All users are identity-verified to maintain authenticity and safety. 24/7 AI Moderation: We run continuous AI verification on profile content, posts, and real-time chat to prevent spam, abuse, and inappropriate content. Text-to-Profile UX: Users read daily self-written introductions first, and profiles only unlock after reading the text. Current Situation: We received a 4.3(b) rejection stating that the app primarily includes dating features duplicating existing apps on the App Store. We appealed to the App Review Board (APL527511) and explained our rebuilt UX (removing photo grids, prioritizing text/diary entries), but received a template rejection stating the category is saturated. We have requested an App Review Appointment and are waiting for guidance. Questions for the Community: Has anyone successfully overcome 4.3(b) for a dating/social app by reframing metadata, category placement (e.g., Lifestyle/Mental Wellbeing instead of Social Networking), or onboarding flows? Is a 4.3(b) flag tied permanently to a Bundle ID once flagged multiple times, or is it possible to pass review after adjusting the core positioning? How did you effectively demonstrate to the review team during an App Review Call that your app provides a non-traditional, unique user experience? Any insights, experiences, or advice would be greatly appreciated. Thank you!

Our developer account was deactivated, and our app has now been unavailable for more than a week. We submitted our appeal and contacted Apple regarding Case ID 20000149095871, but we still have not received a substantive response. We have worked with Apple for approximately three years and have always had great respect for the App Review team and Apple’s rules. Whenever App Review raised concerns in the past, we communicated openly with the team, understood the issue, and made the requested changes. That is why we were genuinely shocked and deeply concerned by what happened. We are not asking Apple to make an exception for us. We are simply asking for the opportunity to understand what went wrong and fix it. Our team is ready to provide any information, make any necessary corrections, or speak directly with Apple by phone. After three years of cooperation and respect for Apple’s team, it is very difficult for us to understand why our app has been unavailable for more than a week while we are still waiting for an answer. We sincerely hope someone from Apple can review our situation and escalate Case ID 20000149095871 to the appropriate team. We just want the opportunity to understand the issue, cooperate with Apple, and resolve this properly. Thank you for your attention and help.

Hello, My app has been in "In Review" status since August 4, 2026, which is now 27 days. App ID: 1621086524 Status: In Review since Aug 4, 2026 Support case ID: 20000147051607 At the moment: No Resolution Center messages No metadata issues shown in App Store Connect No requests for additional information Agreements, Tax, and Banking all show Active I submitted an App Review Status request through the contact form on the case above and have not received a response. Could you confirm whether additional documentation or information is required from me to complete the evaluation? I am happy to provide the bundle ID, entity and licensing documentation, demo account credentials, or export compliance details. Thank you.

Hi everyone! I see a lot of people complaining about the same issue: their apps have been stuck in “Waiting for Review” or “In Review” for more than 48 hours. I think Apple should reconsider the wording of their automated email. When they say that 90% of apps are reviewed within 48 hours, it feels quite ambiguous because it doesn’t really explain what happens with the remaining 10%. I see many people waiting more than 48 hours for a review, just like I am. I submitted my app on July 30, 2026, and it still hasn’t been reviewed. The status is still “Waiting for Review.”

I am really disappointed with the recent app store time review. I have been waiting for 2 weeks for being reviewed. They rejected our release and again I have to wait for other 2 weeks or maybe more. They really don't care about your business at all.

I am having difficulty getting clarification from App Review regarding an external tip link and Guideline 3.1.1. My app is distributed exclusively on the United States App Store storefront. It is a free app, and the "About" page contains an optional “Buy Me a Coffee” link that opens an external browser. The tip does not unlock any content, functionality, subscription, service, or other benefit in the app. App Review has told me that the link must be replaced with In-App Purchase and cited the following language from Guideline 3.1.1: “We understand you have reviewed the updated App Review Guidelines and have questions regarding whether apps are still required to use in-app purchase to process "tips" for developers and digital content creators. Please note that the recent changes to guidelines 3.1.1, 3.1.1(a), 3.1.3 and 3.1.3(a) have not changed the scenarios where In-App Purchase is required. Guideline 3.1.1 states in part, "Apps may use in-app purchase currencies to enable customers to "tip" the developer or digital content providers in the app." To resolve the issues with your current submission, it would be appropriate to revise the app to use in-app purchase to process "tips" for developers and digital content creators. Please let us know if you have further questions. We look forward to reviewing the app once the appropriate changes have been made.” I am having difficulty reconciling that interpretation with the current language of Guideline 3.1.1(a), which specifically states that entitlements are not required for buttons, external links, or other calls to action in United States storefront apps. Apple’s May 1, 2025 guideline update also states that Guidelines 3.1.1, 3.1.1(a), 3.1.3, and 3.1.3(a) were changed in response to the U.S. court decision concerning external purchasing links. The 3.1.1 language regarding tips says that apps “may use” IAP for tips; it does not appear to state that an optional tip that provides no digital goods, services, or functionality must use IAP. Has anyone recently dealt with this specific situation for a U.S.-storefront-only app? If so, was an App Review Board appeal required to resolve it? I am trying to determine whether I am overlooking another provision of the guidelines that specifically requires an optional external tip to use IAP in a United States storefront app. I have a pending appeal but am frankly disappointed in this situation and I do not want to wait weeks or months to get this through the appeal process.

Hi all, My app has been stuck in the "Waiting for Review" status since August 13 (US Time), and today is August 23. It has been 10 days without any status updates or messages from the App Review team. App ID: 6800282515 Submission Date: Aug 13, 2026 Developer Support Request Submitted: Aug 19 (No response yet) Expedited Review Requested: Aug 20 (No response yet) Current Status: Waiting for Review Since both support inquiries and expedited requests haven't received a reply after several days, I am concerned there might be an internal system hold or communication breakdown regarding this submission. Could someone from Apple please look into this or advise if any additional documentation/action is needed from my side? Thanks for your help!

Hi App Review, I have an update to a live app that has now spent roughly 10 weeks unable to get through review, across two separate submissions, and I'd appreciate someone checking whether it's genuinely queued or whether something is holding it. Timeline: 16 June 2026 — v1.1.0 submitted. Sat in "Waiting for Review" for 5+ weeks, never moved to In Review. No Resolution Center message, nothing action-required. 23 July 2026 — after that submission showed no movement, I removed it and submitted a fresh build of the same version. It has now been in "Waiting for Review" for 38 days, again with no reviewer pickup and no Resolution Center message. v1.0.0 reviewed and approved normally on 8 June 2026, so the app and account have a clean prior review. The resubmission has been left completely untouched — no edits, no cancellations — so this is not a case of repeated changes resetting the queue. Two clean submissions of the same update have now stalled identically. What I've already checked on my side: no Resolution Center messages, no action-required banners, build shows valid and correctly attached to the version, export compliance answered, and Agreements/Tax/Banking all current. I've also raised support case 102923511308 and submitted an expedited review request, neither of which has changed the status. Could someone confirm whether this submission is proceeding normally, or flag if anything is required from me or if it needs to be looked at manually? Happy to provide the submission ID or any other detail. @Apple

Hi everyone, I’m a developer maintaining an existing app that has been live on the App Store for many years. We regularly submit updates, and normally our submissions are reviewed and approved within 48 hours without any issues. However, I’m currently experiencing an unusual situation and would appreciate some advice. 19 August: I submitted a new version of the app. It went into review but was rejected under: Guideline 1.1 - Safety - Objectionable Content The app’s marketing includes terms or images that reference objectionable content or services. These references can be found in the app’s metadata, including, but not limited to, the following metadata field(s): description and name. I’m not sure what triggered this rejection because the app name and description have not been changed for years. The app has been live and regularly reviewed during that time without this issue. The rejection also did not identify the specific wording or content in the app name or description that was considered objectionable. I responded to the review team explaining the situation and asked them to identify the specific part of the metadata that caused the issue so that we could review and update it if necessary. However, I did not receive any further response. I also submitted an appeal, but I have not received a response after several days. 21 August: Because we still need to maintain the app and release updates, I cancelled the previous submission and submitted a new version for review. However, this submission has also remained pending and has not moved forward to review. 25 August: I cancelled the submission again and created another submission containing both maintenance updates and a big launch for a new country. This update is important for our business because the new operation is scheduled to launch on 1 September. We need the app update to be reviewed and approved before then. I have also submitted an expedited review request and a new ticket, but it still hasn’t moved forward or been reviewed. My questions Is there anything I can do to get the current submission reviewed, given that the previous submission was rejected and the appeal has not received a response? Could the previous Guideline 1.1 rejection be causing the subsequent submissions to remain pending? Should I continue waiting for the current submission, or is there another recommended process for escalating this situation? The delay is now becoming critical because the new country launch is scheduled for 1 September, and not having the required app update available by then would significantly affect our business operations. Any advice from other developers who have experienced a similar situation would be greatly appreciated. Thank you.

Hello, My app, Pellix, has been stuck in “Waiting for Review” for approximately 9 days, and the review process has still not started. I contacted Apple Developer Support 3 days ago, but I have not received any response yet. There are also no outstanding actions or messages in App Store Connect. Submission ID: 383b92d9-bc90-4be4-bd66-d0b8ecd53966 Case ID: 20000146897751 Could someone from the App Review team please confirm whether my submission is correctly queued for review or help escalate the existing support case? Thank you.

Hello App Review Team, I’m seeking confirmation that my first iOS app submission is correctly queued for review. DriveAvionn 1.0 was originally submitted as a new app and remained in Waiting for Review for an extended period. App Review subsequently requested additional information under Guideline 2.1, including a physical-device screen recording and details regarding the app’s functionality, target audience, testing environment, external services, regional operation, and access instructions. We provided the requested information in full, including a continuous physical-device recording demonstrating account creation and verification, both vehicle-search workflows, messaging, billing, account settings, and account deletion. The separate App Review test account remains active and available. The submission was then successfully resubmitted and is currently again showing Waiting for Review. There are no outstanding messages or compliance items visible in App Store Connect, and no purchase is required to review the app. Given the unusually long review times currently being reported for first submissions, could someone from App Review please confirm that this submission is properly queued and that no additional action is required on our side? Thank you for your assistance.

Hello, Our new app TruckSOS (Apple ID: 6801003473) was submitted for review on August 15, 2026. On August 16 we received a Guideline 2.1 (Information Needed) request with seven items, including a screen recording of the app running on a physical device. On August 18 we replied in the Resolution Center with all seven requested items, including a full 11-minute screen recording captured on a physical iPhone running iOS 26.3.1 (account creation, login, core flows, UGC reporting and blocking, permission prompts, and account deletion). Since then there has been no response of any kind. Timeline: Aug 15: version 1.0 submitted (submission ID 7cc57105-24c7-4300-ab4d-73a47aa9e82f) Aug 16: Guideline 2.1 - Information Needed request Aug 18: full reply with all requested information and the screen recording attached Aug 25: polite follow-up in the same thread - no answer Expedited review request refused by the form with "You don't have a submission in review" (the submission is in "Unresolved Issues" status) Aug 26: accepted the updated Program License Agreement in case it was blocking anything - no change Aug 28: wrote to Developer Support - no reply yet It has now been 12 days since we provided everything that was requested and the review appears to be stalled. Is there anything else we should do, or could someone from the App Review team take a look? Thank you!